|
|
|
FAQ Hardware
|
|
|
FAQs: Hardware/Driver > General
[Number of FAQs 11]
1. Where can I check for the resources (IRQ and Address) assigned to my CAN interface board?
In the IXXAT Interfaces Applet (VCI V2) in control panel:
If you double click on the CAN Interface board, the assigned IRQ and address will be displayed.
This IRQ and address should be confirm to the settings of the operating system.
Under Windows 9x/ME:
In the device manager:
Start | Settings | Control panel | System | Device manager | IXXAT CAN-Interfaces | CAN-Interface | Settings | Resources
Under Windows NT (Service Pack 5):
Start | Program | General administration | Windows NT Diagnose | Resources | IRQ / Address
Under Windows 2000 (Service Pack 1)/XP:
Start | Settings | Control panel | System | Hardware | Device manager | IXXAT CAN-Interfaces | CAN-Interface | Settings | Resources |
|
2. Is there an activatable CAN termination resistor on my CAN interface board?
There are no CAN termination resistors on our CAN interface boards (except for CANrepeater). But we can offer a 9 pin Sub-D connector with an implemented CAN termination resistor. |
|
3. Where is the time stamp for the received CAN messages generated?
The microcontroller on the active CAN interface board generates the time stamp for the received CAN messages. On the passive CAN interface board the VCI generates the time stamp for the received CAN messages. |
|
4. Why can´t I receive the Remote-Frames with the Intel 82527 Full CAN Controller?
The Intel 82527 Full CAN Controller can not provide the received Remote-Frames transparent for the VCI-Applikation (Limitation of the Intel Full CAN). |
|
5. The CAN Interface does not run after returning from the sleep mode (or hibernate mode)
The active CAN Interfaces must be reinitialized after returning from the sleep mode (or hibernate mode) because the firmware is in it´s volatile memory and therefore not longer available after returning from the sleep mode.
|
|
6. I installed a new operating system. What should I do to get my CAN Interface running again?
Please check if the CAN Interface is supported by this operating system. You can find the VCI compatibility table in the support area on our web page. Download the VCI installation manual and the current VCI version from the download area on our web page and install the VCI as described in the VCI installation manual. Please note the installation tips on our web page in the support area. |
|
7. Most used CAN-baudrates:
Bittiming register values for most used CAN-baudrates for CAN-Controller with 16 MHz clock frequence. (CIA unstandardized CAN-Baudrates)
Baudrate
(kBd) |
BTR0
(hex) |
BTR1
(hex) |
46,08
|
52 |
24 |
47,6 |
C6 |
EF |
47,6 |
C6 |
FE |
47,6 |
C7 |
CE |
62,5 |
C7 |
3A |
75 |
- |
- |
74 |
8B |
15 |
76 |
C6 |
39 |
83,3 |
85 |
2B |
95 |
85 |
47 |
111 |
45 |
18 |
The Values for the SJA1000 with 20 MHz clock frequence
Baudrate
(kBd) |
BTR0
(hex) |
BTR1
(hex) |
1000
|
00 |
16 |
500 |
40 |
2F |
250 |
41 |
2F |
125 |
43 |
2F |
100 |
44 |
2F |
50 |
49 |
2F |
20 |
58 |
2F |
10 |
71 |
2F |
|
|
8. Is a CAN interface board with or without galvanic isolation more suitable for my CAN network?
A CAN interface board with galvanic isolation is more noise immune and prevents mass grinding. The potential difference occurring because of the different power supplies for different CAN nodes does not influence the transmission quality.
The galvanic isolation reduces the maximal possible CAN bus length by approximately 10 meters. (The typical CAN signal delay of the galvanic isolation is approximately 50ns).
Please note, that the CAN_GND wire has to be connected even if a galvanic isolation is used. |
|
9. Why doesn’t my CAN interface board run correctly?
Please fill out the problem report form completely
(Which CAN interface board, VCI version, operating system etc. are used?)
and answer the following questions in the field „Detailed description of the problem“:
- Is the CAN interface boad supported under the used operating system with the used VCI version?
(see the VCI compatibility table in the support area on our webpage)
a) Please send us a screenshot of the list with installed IXXAT software (see „Start | Control panel | Software | VCI version“)
- Are or were on the PC any older VCI versions, older canAnalyser versions or older CANopen Master API versions installed?
Please note:
a) The canAnalyser versions up to v1.71 installs the VCI v1 automatically.
b) The CANopen Master API versions up to v2.2 installs the VCI v1.
c) The VCI v1 and VCI v2 are incompatible. Please start the VCI-Cleaner after the deinstallation of the VCI V1 as described in the VCI update instructions in the VCI v2 installation manual.
(You can find the current VCI version, VCI-Cleaner, VCI installation manual in the support area on our webpage.)
- Is the CAN interface board successfully detected in the device manager?
Please send us a device manager screenshot with the opened „IXXAT ...“ entry.
(see „Start | Control panel | System | Hardware | Device manager | IXXAT“ )
Please note:
a) If there is no „IXXAT CAN interfaces“ entry (for VCI v2) and no „IXXAT VCI V3 interfaces“ entry (for VCI v3) in the device manager, please delete (uninstall) the „Unknown device“ entry from the device manager and check if the CAN interface board will be detected successfully after the PC reboot.
- If the CAN interface board is detected in the device manager with any ressource conflicts, please delete (uninstall) the CAN interface board entry and check if the problem still occurs after the hardware redetection after the PC reboot. If yes, please send us screenshots with ressource conflict description and ressource allocation.
(see „Start | Control panel | System | Hardware | Device manager | View | Ressources by type | Memory & E/A & IRQ“)
Please note:
a) For ISA slot boards the used IRQ has to be reserved in BIOS for ISA slot as described in the VCI installation manual.
- Does the CAN interface board run correctly with the Minimon?
Please select the correct CAN interface board in the Minimon, initialize the CAN interface board with the correct CAN baudrate and tell us if the CAN interface board could be initialized successfully and if it can transmit and receive CAN messages. If not, please send us the error screenshot.
Please note:
a) In the Minimon/32 (VCI V2) the CAN interface board has to be selected correctly before the start. Please click on the button „>“ and select the CAN interface board.
b) If the VCI V2 is used, please test the CAN interface board using the IXXAT interfaces applet in the control panel and send us the screenshot of the test result.
- If the Minimon initialized the CAN interface board successfully, but it is not possible to transmit and receive CAN messages, please answer the question of the FAQ entry „Why doesn’t my CAN bus run correctly?“
- Does the CAN interface board run correctly on another PC?
(If the CAN interface board runs correctly on another PC, then a hardware problem can be excluded.)
- Does another CAN interface board run correctly on the PC?
(If another CAN interface board of the same type runs correctly on the PC, then the CAN interface board has to be sent for repair.)
- Please tell us the exact PC type.
(motherboard type, clock frequency, USB controller type, PCMCIA controller type...) (For this you can use Aida32, SiV (System Information Viewer) ect.)
- Is the USB/CAN interface board connected directly or via an external USB Hub with an external power supply?
(Please tell us the USB Hub type if one is used.)
Which USB devices are connected?
|
|
10. Why doesn’n my CAN bus run correctly?
Please answer the following questions:
- Are all CAN nodes connected correctly with each other?
a) Are the CAN cable and CAN connectors alright?
(You can find the CAN connector pin assignment in the support area on our webpage.)
b) Is the CAN cable shielded?
c) Is a standard CAN cable used?
d) Are CAN_H, CAN_L and CAN_GND of the CAN nodes connected with each other?
- Is the CAN bus terminated with two CAN termination resistors?
- Is the maximal CAN bus length not exceeded?
- Are at least two CAN nodes connected to the CAN bus?
Please note:
a) For CAN communication at least two CAN nodes are required, because of the CAN acknowledgement.
b) CAN nodes in „Listen Only“ mode do not send the acknowledgement.
- Is the same CAN baudrate set for all CAN nodes?
- Is the same CAN mode set for all CAN nodes?
(standard (11bit ID) or extended (29bit ID)?)
- Do all CAN nodes work according to the same CAN standard?
(ISO 11898 [ISO99-2] (CAN-High-Speed) or ISO 11519 [ISO99-3] CAN-Low-Speed (Fault-Tolerant)).
- Are electrical disturbances on the CAN bus?
- Are Error Frames on the CAN bus?
- Please send to us a CAN topology scheme with the following data
a) Wire length
b) CAN baudrate
c) Location of both CAN termination resistors
d) Number and type of connected CAN nodes
- Could you successfully test the CAN bus with the CANcheck or CAN-Bus-Tester?
- Please send us an oscilloscope screenshot of the CAN signal.
|
|
11. Why the CAN-Transceiver on my CAN interface board got broken?
The CAN transceiver can bear an external overvoltage about +/- 36V on CAN_H and CAN_L referenced to CAN_GND.
An external overvoltage more than +/- 36V can destroy the CAN-Transceiver.
The possible causes for an external overvoltage on the CAN bus:
1. Electric disturbances on the CAN bus (generated by electric motors, variable-frequency drive, lightning…)
A shielded CAN cable reduce the induced electric disturbances.
2. Large differences of the voltage potentials between different CAN nodes if the CAN_GNDs are not connected with each other.
(We recommend connecting CAN_GND of all CAN nodes with each other for the compensating electric current, especially when using CAN interface boards with galvanic isolation).
3. A wrong wiring, that connect CAN with an external power supply (>36V).
4. Analysing a CAN bus system using a CAN interface board, please connect the CAN bus while it is not running to avoid possible ESD problems.
|
|
|
|
|